Update date references for 2026-05 triage (#2861)#2872
Conversation
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Hi @santihdzs, did you generate this PR using an LLM? it's ok if you did, but please disclose beforehand that you did so.
| # `minicore` test auxiliary: using `core` stubs | ||
|
|
||
| <!-- date-check: Oct 2025 --> | ||
| <!-- date-check: May 2026 --> |
There was a problem hiding this comment.
I don't see any date here at all. Can we just remove the date-check comment?
There was a problem hiding this comment.
I don't see any date here at all.
@jyn514 what does this mean
| ## `RUSTC_BOOTSTRAP` and stability | ||
|
|
||
| <!-- date-check: Nov 2024 --> | ||
| <!-- date-check: May 2026 --> |
| <!-- date-check --> Nov 2025 | ||
| <!-- date-check --> May 2026 | ||
| ``` | ||
|
|
||
| Example: | ||
|
|
||
| ```md | ||
| As of <!-- date-check --> Nov 2025, the foo did the bar. | ||
| As of <!-- date-check --> May 2026, the foo did the bar. | ||
| ``` | ||
|
|
||
| For cases where the date should not be part of the visible rendered output, | ||
| use the following instead: | ||
|
|
||
| ```md | ||
| <!-- date-check: Nov 2025 --> | ||
| <!-- date-check: May 2026 --> |
There was a problem hiding this comment.
this is in the contributing guide and not tied to anything specific. it doesn't need updating.
| @@ -1,4 +1,4 @@ | |||
| <!-- date-check: Jul 2025 --> | |||
| <!-- date-check: May 2026 --> | |||
| When interfacing with the type system it will often be the case that it's necessary to request a type be normalized. There are a number of different entry points to the underlying normalization logic and each entry point should only be used in specific parts of the compiler. | ||
|
|
||
| <!-- date-check: May 2025 --> | ||
| <!-- date-check: May 2026 --> |
| a lot of `rustdoc`'s architecture was designed around not doing that, but a | ||
| `TyCtxt` is now passed to `formats::renderer::run_format`, which is used to | ||
| run generation for both `HTML` and the (unstable as of <!-- date-check --> Nov 2025) JSON format. | ||
| run generation for both `HTML` and the (unstable as of <!-- date-check --> May 2026) JSON format. |
|
Reminder, once the PR becomes ready for a review, use |
|
@jyn514 apologies for not disclosing upfront, I used an LLM as an aid but reviewed all changes myself before committing, I'll address the review comments now |
56ee20f to
17dd4a7
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
Part of #2861.
Updated date references to May 2026 in:
Skipped lldb-visualizers.md and opaque-types-type-alias-impl-trait.md
as those reference external dependencies needing deeper verification.
r? rust-lang/rustc-dev-guide